Object oriented memory in solid state devices

ABSTRACT

The present disclosure includes methods, devices, and systems for object oriented memory in solid state devices. One embodiment of a method for object oriented memory in solid state devices includes accessing a defined set of data as a single object in an atomic operation manner, where the accessing is from a source other than a host. The embodiment also includes storing the defined set of data as the single object in a number of solid state memory blocks as formatted by a control component of a solid state device that includes the number of solid state memory blocks.

TECHNICAL FIELD

The present disclosure relates generally to semiconductor memorydevices, methods, and systems, and more particularly, to object orientedmemory in solid state devices.

BACKGROUND

Memory devices may be provided as internal, semiconductor, integratedcircuits and/or external removable devices, for instance, in computers,personal digital assistants (PDAs), digital cameras, and mobile (e.g.,cellular) telephones, among various other electronic devices. There aremany different types of memory including random access memory (RAM),read-only memory (ROM), dynamic random access memory (DRAM), synchronousdynamic random access memory (SDRAM), phase change random access memory(PCRAM), and flash memory, among other types of memory configurations.

Various types of memory may be used in systems using memory devices. Thevarious types of memory may be used in any combination to provide memoryfor a host. For instance, flash memory (e.g., using NAND or NOR memorycells) may be included in a memory device. Flash memory may be utilizedas internal memory or as removable memory, which may be coupled to thesystem through an interface, such as a universal serial bus (USB)connection.

Flash memory devices may be utilized as non-volatile memory for a widerange of electronic applications. Flash memory devices may use aone-transistor memory cell that allows for high memory densities, highreliability, and low power consumption.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of a system in accordance with one ormore embodiments of the present disclosure.

FIG. 2 illustrates a diagram of a portion of a memory array inaccordance with one or more embodiments of the present disclosure.

FIG. 3 is a block diagram illustrating object oriented memory in solidstate devices in accordance with one or more method embodiments of thepresent disclosure.

DETAILED DESCRIPTION

The present disclosure includes methods, devices, and systems for objectoriented memory in solid state devices. One embodiment of a method forobject oriented memory in solid state devices includes accessing adefined set of data as a single object in an atomic operation manner,where the accessing is from a source other than a host. In variousembodiments, the source can be, by way of illustration and not by way oflimitation, a network as described with regard to FIG. 1. The embodimentalso includes storing the defined set of data as the single object in anumber of solid state memory blocks as formatted by a control componentof a solid state device that includes the number of solid state memoryblocks.

A solid state device can include a number of memory devices (e.g., anumber of memory chips). As utilized in the present disclosure, using “anumber of” to refer to a thing can refer to one or more such things. Forinstance, a number of memory devices can refer to one or more memorydevices. As one of ordinary skill in the art will appreciate, a memorychip can include a number of dies. Each die can include a number ofmemory arrays and peripheral circuitry thereon. A memory array caninclude a number of planes, with each plane including a number ofphysical blocks of memory cells. Each physical block can include anumber of pages of memory cells that can store a number of sectors ofdata.

In order to achieve low latency and high bandwidth operations acrosslarge storage capacity, solid state devices may include multiplechannels operating in parallel, with each channel operating some portionof memory. Thus, multiple copies of a memory channel controller (e.g.,NAND flash controller logic) may be integrated on a solid state device'smulti-channel system controller. In such an arrangement, each channel,or an aggregation point of the channels, may be tasked with operatingthe associated memory served by the channel, including performinglogical to physical mapping and/or block management (e.g., wearleveling). Therefore, each copy of the multiple memory channelcontrollers, corresponding to each of the multiple channels, may havehigh speed buffer memory used to carry out the mapping and blockmanagement functions. In addition, each copy of the multiple memorychannel controllers may include buffer memory for “in-flight” datadirected to a respective channel.

Memory devices may be combined together to form a solid state device. Asolid state device may include non-volatile memory (e.g., NAND flashmemory and/or NOR flash memory) and/or may include volatile memory(e.g., DRAM and/or SRAM), among various other types of non-volatile andvolatile memory.

A solid state device may be used to replace hard disk drives as the mainmemory device for a computer, as the solid state device may haveadvantages over hard drives in terms of performance, size, weight,ruggedness, operating temperature range, and/or power consumption. Forexample, solid state devices may have superior performance when comparedto magnetic disk drives due to their lack of moving parts, which mayameliorate seek time, latency, and/or other electro-mechanical delaysassociated with magnetic disk drives. Solid state device manufacturersmay use non-volatile flash memory to create flash solid state devicesthat may not use an internal battery supply, thus allowing the drive tobe more versatile and compact.

For some memory applications, solid state devices may be used as areplacement or complement to hard disk drives. In these instances, solidstate devices may be placed in an environment designed to accommodate ahard drive's functions. Due to the differences in granularity orquantization of the smallest erasable unit between solid state devicesand hard drives (e.g., a 512 byte sector for hard drives versus a 128 kor 256 k block in solid state devices), a solid state device that isused as a replacement for or complement to a hard drive in a computingdevice may not operate at peak performance levels.

Parallel communications between each copy of the multiple memory channelcontrollers and the corresponding portions of memory may requireapproximately 20 pins to establish data, control, power, and groundconnections therebetween. This can result in an expensive memory systemhaving a large pin count to ensure compatibility with existing diskdrive protocols.

Development and adoption of solid state devices has been driven by arapidly expanding need for higher input/output performance. Highperformance desktop computers, laptops, mobile systems or devices,and/or any application that needs to deliver information in real-time ornear real-time can benefit from solid state devices. Historically, solidstate devices have been more expensive than hard drives. Due toimprovements in manufacturing technology and expanded chip capacity,however, prices have dropped, leading both consumers andenterprise-level customers to re-evaluate solid state devices as viablealternatives to previous memory systems.

A memory cell stores digital information in a structure that can berapidly switched between more than one readily discernable states. Somememory cells are based on the presence or absence of electrical chargecontained in a region of the cell. By retaining its charge, the memorycell retains its stored data. Some memory cell structures inherentlyleak charge, and must be continually powered to refresh the storedcharge.

Non-volatile memory, however, does not require electrical power toretain charge information. For instance, flash memory may have a“floating gate” upon which the charge is stored, which is insulated tominimize charge leakage. Thus, power is required only to change thestored information (e.g., data, bits, etc.), for instance, to write to(e.g., store charge), to read from (e.g., determine if charge ispresent), and/or to erase (e.g., remove charge) a memory cell. Thenon-volatility of stored data in flash memory is advantageous inportable electronic applications. Non-volatile memory may be used in, byway of example and not by way of limitation, personal computers (e.g.,desktop and laptop), personal digital assistants (PDAs), digitalcameras, and cellular telephones, among many other uses. Program codeand system data, such as a basic input/output system (BIOS) used incomputing systems, among other types, may be stored in non-volatilememory devices.

A solid-state memory device may be a memory device that storespersistent data on solid-state flash memory. Solid state memory devicesare not hard drives, in the traditional sense of the term, because thereare no moving parts involved instead, a solid-state memory device has anarray of semiconductor memory organized using integrated circuits (ICs)rather than magnetic or optical media.

This arrangement has many advantages. Data transfer to and from solidstate devices is faster than electromechanical disk drives. Seek timeand latency may also be reduced. Users enjoy much faster boot timesand/or functionality of operating systems as well. In general, solidstate devices are also more durable and quieter, with no moving parts tobreak or spin up or down. Solid state devices do, however, have a setlife expectancy because there is a finite number of erase/write cyclesbefore performance may become erratic.

Hence, a defined set of data may be rewritten periodically due, forinstance, to “wear” on the memory cells to which the defined set of datawas previously stored. In various embodiments as described in thepresent disclosure, a defined set of data can include a complete,integrated package of “critical data” that can include instructions toenable proper system performance, as defined prior to and during accessof such data and/or after storage of such data. In some embodiments, the“set” of data can be defined as multiple packages of data that becomeintegrated during and/or after accessing such data but prior to storingthe complete, integrated package as the defined set of data.

Moreover, advancements in technology may make replacing of previouslystored (e.g., written) sets of defined data desirable. In the presentdisclosure, each of these operations can be termed “updating” thedefined set of data. Especially for critical data (e.g., for boot imagesand/or operating systems upon which operability of a system depends upona substantially error-free read thereof), it can be important tovalidate the accuracy of such data before storing the defined set ofdata to the solid state memory, in particular when the newly accesseddata replaces data relied upon by a host (e.g., a host device and/or asystem that is managed by the host device) for proper operability.

Existing solid state memory (e.g., NOR and/or NAND flash memory) insolid state devices may store, for instance, host data (e.g., a file) asa series of fixed length logical blocks. The host may maintain a tablethat not only identifies which logical blocks within the flash memorydevice are associated with each file but also the ordering of thoselogical blocks to create the file. Read and write access to the memorydevice by the host may be performed using the logical block numbers.However, the flash device may lack enough information to understand howthe reads and writes relate to the underlying file data itself.

Despite this, the memory system may work well enough for many types ofhost data but may have particular deficiencies for some data types. Oneexample is system data such as processor boot instructions and/oroperating system instructions crucial to operability of a system thathas functions dependent on substantially error-free reading of codedinstructions. Corruption of this type of data may render such a systeminoperable. An alternative memory mechanism is described in the presentdisclosure that provides for increased reliability and performance,along with a broader range of services. As described in the presentdisclosure, the alternative memory mechanism can utilize object orientedmemory in solid state devices and/or block oriented memory that isgoverned by an encoded set of rules to mimic object oriented memory, forexample.

Rather than treating a file as a series of logical blocks (e.g., in ablock oriented manner), the defined set of data in a file can instead betreated (e.g., accessed and/or stored) as one single object (e.g., acomplete, integrated package) by a solid state memory device. Treatingthe defined set of data as a single object can allow the solid statememory device (e.g., having a number of non-volatile NOR and/or NANDflash memory arrays) to perform certain operations during write and readprocesses that can increase reliability and performance. Examples ofsuch operations, which can be performed on data upon which asubstantially error-free read is required for operability of particularsystem functions, can include: a read-verify where a type of dataintegrity check is performed before the write process is performed orconsidered complete; multiple copies of such data are stored so that, incase of a read failure with one copy, the system can rely on a read ofanother one of the copies; and a previous known-good version of the datais maintained so that, in case of a faulty read or re-write, the systemcan be directed to a read of the last known-good data; among otheroperations described herein.

Object oriented data structures in a solid state device, as described inthe present disclosure, can provide and/or assist in providing thejust-described operations, whereas traditional block oriented memorydevices may be incapable of such operations. As described in the presentdisclosure, a solid state device can include a number of solid statememory arrays and a solid state device controller, among othercomponents. The controller can be a control component that manages(e.g., directs, controls, regulates, etc.) the solid state device usinginstructions (e.g., executed by a processor where appropriate) stored assoftware, firmware, and/or hardware (e.g., logic such as an applicationspecific circuit (ASIC)). The present disclosure will enable one ofordinary skill in the art to practice these operations, among others,with embodiments for object oriented memory in solid state devices, alsoreferred to herein as “object oriented solid state devices”.

When writing as object oriented memory in solid state devices, a solidstate device can access a data stream in a block oriented device manner.However, because the object oriented memory device can access the datastream with an understanding that the data stream is associated with asingle defined entity (e.g., a defined set of data that defines a singleobject), a write completion acknowledgement response to, for example, ahost can be delayed until one or more data protection operations havebeen successfully completed. Performance of a variety of data protectionoperations can be facilitated through use of object oriented memorytechniques. A number of these data protection operations are describedbelow.

The solid state device can use properties associated with the object toimprove the reliability of the object data read by the host. The solidstate device can use multiple copies to reduce likelihood that a mediaerror would corrupt the object as read by the host. A variety ofoperations can be performed individually or in combination to enablesuch a reduction in likelihood, as described in more detail below. Forexample, a fail-over operation can use another copy of the object in acase where error detection indicates a read and/or write failure. Insome embodiments, a bit-by-bit comparison can be performed on multiplecopies of the object after error detection in at least one of thecopies. Discrepancies found in the comparison can result in a majorityvote of the multiple copies or the solid state device can revert to thelast known-good object. Another level of validation can be a completecyclic redundancy check (CRC) of the entire object.

The object oriented solid state device can direct the host to previouslystored versions of the entire object. For example, a control componentof the object oriented solid state device can detect multiple readrequests to the object within a particular period of time (e.g., whichcan be a predetermined period or determined “on the fly”, as appropriateto the circumstance) and recognize such multiple requests as anindicator that the device is caught in a re-boot loop. Such recognitioncan result in the solid state device providing the host with a lastknown-good version of the object.

The object oriented solid state device can, in various embodiments,provide services to expedite booting of the host. Among these services,the solid state device can automatically initiate a read operation basedupon a particular event, such as a power-on reset and/or transition of asignal, among other events. The read data can then be automatically sentto the host where it can be used, for example, to boot the host and/orthe system that includes the host or the data can be ignored if the datais not required by the host and/or the system that includes the host atthat time.

Block oriented memory devices may not be able to perform the range ofoperations and/or services described herein because block orientedmemory devices generally do not have a capability to be aware of thenumber of logical blocks in a file and/or the order in which the blockswill be read and/or written. Block oriented memory devices generallyonly respond to read/write commands.

Before a computing device accomplishes a desired task, it may receive anappropriate set of instructions. Executed by, for instance, a device'sprocessor(s), these instructions direct the operation of the device.These instructions can be stored in a memory. Instructions can invokeother instructions. A computing device and/or system (e.g., a server,router, desktop computer, laptop, mobile devices or systems, and otherdevices having processor logic and memory) can include an operatingsystem layer and an application layer to enable performing variousfunctions or roles. The operating system layer may include a “kernel”(i.e., master control program) that provides an underlying level ofcontrol and operability. The kernel may provide task management, devicemanagement, and data management, among others, to, for instance, a host.The kernel may set the standards for application programs that run onthe computing device and may control resources used by applicationprograms. The application layer may include programs (i.e., executableinstructions) which are located above the operating system layer andaccessible by a user.

A boot image and/or operating system instructions may contain encodedinformation (e.g., a defined set of bits) that enables initiation of thejust-described functions and thus can be called critical data. Accessingand/or storing such critical data in an object oriented manner shouldassist in preserving the integrity of the critical data in order tomaintain operability of systems controlled, for example, by a host.

As described in the present disclosure, instructions are provided thatexecute to protect critical data. One or more embodiments are providedthat execute instructions such that after a new defined set of data hasbooted successfully as stored at least once, whether in association withan operating system installation or update, the new defined set of datais automatically saved as “last install”. The last install configurationwill be a “known good” installation and help to avoid issues when, forexample, a user inadvertently creates a non-bootable kernelconfiguration and has not created a backup. One or more embodiments areprovided that execute instructions to make a number of copies of one ormore defined sets of critical data. One or more embodiments are providedthat execute instructions that can execute to apply error correctionoperation to the copy. These and other embodiments will be appreciatedby one of ordinary skill in the art upon reading this disclosure.

FIG. 1 illustrates a block diagram of a system in accordance with one ormore embodiments of the present disclosure. In the following detaileddescription, reference is made to the accompanying drawings that form apart hereof and in which is shown by way of illustration how one or moreembodiments of the disclosure may be practiced. These embodiments aredescribed in sufficient detail to enable those of ordinary skill in theart to practice the embodiments of this disclosure, and it is to beunderstood that other embodiments may be utilized and that process,electrical, and/or structural changes may be made without departing fromthe scope of the present disclosure. As used herein, the designators“N,” “M,” “R,” and “S,” particularly with respect to reference numeralsin the drawings, indicates that a number of the particular feature sodesignated can be included with one or more embodiments of the presentdisclosure.

The figures herein follow a numbering convention in which the firstdigit or digits correspond to the drawing figure number and theremaining digits identify an element or component in the drawing.Similar elements or components between different figures may beidentified by the use of similar digits. For example, 130 may referenceelement “30” in FIG. 1, and a similar element may be referenced as 230in FIG. 2. As will be appreciated, elements shown in the variousembodiments herein can be added, exchanged, and/or eliminated so as toprovide a number of additional embodiments of the present disclosure. Inaddition, as will be appreciated, the proportion and the relative scaleof the elements provided in the figures are intended to illustrate theembodiments of the present invention, and should not be taken in alimiting sense.

A system may include a host, host memory, and a number of memory devicesexternal to the host. The host may have a number of processors, a hostcontroller, and a host controller memory that is associated with thehost controller, and a number of internal memory devices. The host mayuse the internal and/or the external memory devices by interacting withthe memory devices via the host controller. The host controller maycommunicate with the memory devices to perform operations on the memorydevices, such as reading data from the memory devices to the host orstoring data from the host in the memory devices. The commands thatmanage the reading and storing of data may be built by the host. Thehost controller may have hardware that controls the memory devicecapabilities in the commands. In such cases, when the host controllerhas hardware that defines the memory devices capabilities, the hostcontroller may be limited to building commands that have thecapabilities associated with the hardware that is on the hostcontroller.

In one or more embodiments, the system 100 illustrated in FIG. 1 can beutilized to enable functionality, by way of example and not by way oflimitation, for personal computers and/or a laptop computers, mobiletelephones, digital cameras, digital recording and play back devices,PDAs, memory card readers, and interface hubs, and USBs, among otherexamples.

The system 100 can include a host 105, where the host 105 includes atleast one host processor 114 that communicates with a number of othercomponents via a host controller 112. The other host components mayinclude a host memory 118 accessed via a host memory controller 122.Additional components may include a host network interface 110 and auser interface 125.

In various embodiments, the host network interface 110 can allowaccessing (e.g., communication with) an outside network 102 to enableinput and output device interaction with the network 102. By way ofexample and not by way of limitation, such outside networks can includea local area network (LAN), a wide area network (WAN), the Internet,and/or wireless networks, among others. The host network interface 110may be coupled via the network 102 to corresponding interface devices inother devices and/or systems. Network 102 may itself be comprised ofmany interconnected systems and communication links, as the same areknown and understood by one of ordinary skill in the art. Communicationlinks as used herein may be hardwire links, optical links, satellite orother wireless communications links, wave propagation links, or anyother mechanisms for communication of information.

The user interface 125 can, in various embodiments, enable input by anumber of devices that may include a keyboard, pointing devices (e.g., amouse, trackball, touchpad, or graphics tablet), a scanner, atouchscreen incorporated into a display, audio input devices such asvoice recognition systems, microphones, and/or other types of inputdevices (not shown). In general, use of the term “input device” isintended to include all possible types of devices and ways to inputinformation into the system 100 illustrated in FIG. 1.

The host 105 of the system 100 can, in various embodiments, be operablycoupled to a solid state device 150 that provides peripheral memory tothe host 105. The solid state device can, in various embodiments,include a solid state device network interface 156 that can allowcommunication with (e.g., access to) the outside network 102 to enableinput and/or output to the network 102, as previously described.

The solid state device network interface 156 can, in variousembodiments, be operably coupled to a solid state device controller 166.The solid state device controller 166 can, in various embodiments,handle and/or manage input of data/information from and/or output ofdata/information to the solid state device network interface 156.Managing the data/information by the solid state device controller 166may be executed by a processor 172 embedded in, or otherwise associatedwith, the solid state device controller 166. The solid state devicecontroller 166 can, in various embodiments, be operably coupled to thehost controller 112 of the host 105 in order to provide to and/orreceive from (e.g., exchange) the host 105 data/information. Forexample, the data/information (e.g., bits that are encoded in acomputer-readable binary code) can be data/information upon whichoperability of a system controlled by the host 105 depends upon asubstantially error-free read of such data/information. By way ofexample and not by way of limitation, the data/information can be adefined set of data required for booting (e.g., a boot image) and/orinitiating functionality of an operating system in a host and/or asystem managed by the host.

The solid state device controller 166 of the solid state device 150 can,in various embodiments, be operably coupled to a number of solid statememory arrays 186. The solid state memory arrays 186 are described infurther detail in connection with FIG. 2. In brief one or more solidstate memory arrays 186 can, in various embodiments, be utilized tostore, for example, the defined set of data (e.g., after “writing” ofsuch data in memory cells of the memory arrays) as a single object 192upon which operability of the system controlled by the host 105 dependsupon a substantially error-free read of the defined set of data.

As described in the present disclosure, the defined set of data can behandled as a collective whole to be stored in the solid state memoryarrays 186 as one or more single objects 192 and can be provided as suchto the host 105 through the solid state device controller 166 toreliably enable booting and/or operating system functions in the systemmanaged (e.g., directed, controlled, regulated, etc.) by the host 105.As described in the present disclosure, the components 156, 166, 172,186, 192 of the solid state device 150 can, in various embodiments,enable reliable updating of such defined sets of data (e.g., singleobjects), which may be referred to as “critical data”, by handling suchsingle objects in an object oriented manner.

FIG. 2 illustrates a diagram of a portion of a memory array inaccordance with one or more embodiments of the present disclosure.Although not shown in FIG. 2, one of ordinary skill in the art willappreciate that the solid state memory array 230 can be located on aparticular semiconductor die along with various peripheral circuitryassociated with the operation thereof.

As shown in FIG. 2, solid state memory array 230 has a number ofphysical blocks 240-0 (BLOCK 0), 240-1 (BLOCK 1), . . . , 240-M (BLOCKM) of memory cells. The indicator “M” is used to indicate that the array230 can include a number of physical blocks. The memory cells can besingle level cells and/or multilevel cells. In various embodiments ofthe present disclosure, particular physical memory blocks can includeonly single level memory cells (e.g., single-bit memory cells) or thephysical memory blocks can include multilevel memory cells that are onlywritten as single-bit cells. As an example, the number of physicalblocks in array 230 may be 128 blocks, 512 blocks, or 1,024 blocks, butembodiments are not limited to a particular multiple of 128 or to anyparticular number of physical blocks in an array 230.

Further, embodiments are not limited to a particular type of memorybeing used in all of a number of arrays. That is, different memoryarrays can, in various embodiments, use any type of memory blocks aspresently known by one of ordinary skill in the art (e.g., various typesof memory such as non-volatile, volatile, etc.) However, for purposes ofthe present disclosure, the number of memory arrays contains at leastone array that is configured as a solid state memory array, asappreciated by one of ordinary skill in the art. In the embodimentillustrated in FIG. 2, the memory array 230 can be, for example, anon-volatile NAND flash memory array. In some embodiments, by way ofexample and not by way of limitation, the memory array 230 can have anon-volatile NOR flash memory array architecture.

In the example shown in FIG. 2, each physical block 240-0, 240-1, . . ., 240-M includes memory cells which can be erased together as a unit(e.g., the cells in each physical block can be erased in a substantiallysimultaneous manner). For instance, the cells in each physical block canbe erased together in a single operation. Each physical block, e.g.,240-0, 240-1, . . . , 240-M, contains a number of physical rows, e.g.,250-0, 250-1, . . . , 250-R, of memory cells coupled to an access line(e.g., a word line). The indicator “R” is used to indicate that aphysical block, e.g., 240-0, 240-1, . . . , 240-M, can include a numberof rows. In some embodiments, the number of rows (e.g., word lines) ineach physical block can be 32, but embodiments are not limited to aparticular number of rows 250-0, 250-1, . . . , 250-R per physicalblock.

As one of ordinary skill in the art will appreciate, each row 250-0,250-1, . . . , 250-R can store one or more pages (e.g., bits) of data. Apage refers to a unit of programming and/or reading (e.g., a number ofcells that are programmed and/or read together or as a functional groupof memory cells). In the embodiment shown in FIG. 2, each row 250-0,250-1, . . . , 250-R stores one page of data. However, embodiments ofthe present disclosure are not so limited. For instance, in someembodiments of the present disclosure, each row can store multiple pagesof data. For example, each cell in a row can contribute a bit towards anupper page of data, and can contribute a bit towards a lower page ofdata. In one or more embodiments, a memory array can include multiplephysical blocks of memory cells and each physical block can be organizedinto multiple pages. As described in the present disclosure, at leastone array and/or multiple blocks in such an array includes memory cellsthat can only store one page of data or that are utilized in such amanner that they store only one page of data.

In one or more embodiments of the present disclosure, and as shown inFIG. 2, a row, such as row 250-0, can store data (e.g., after a writeoperation) in accordance with a number of physical sectors 252-0, 252-1,. . . , 252-S. The indicator “S” is used to indicate that a row, e.g.,250-0, 250-1, . . . , 250-R, can include a number of physical sectors.Each physical sector 252-0, 252-1, . . . , 252-S can store datacorresponding to a logical sector and can include overhead information,such as error correction code (FCC) information and logical blockaddress (LBA) information, as well as a defined set of data (e.g.,critical data as described in the present disclosure). As one ofordinary skill in the art will appreciate, logical block addressing is ascheme often used by a host for identifying a logical sector ofinformation. As an example, a logical sector of data can be a number ofbytes of data (e.g., 256 bytes, 512 bytes, or 1,024 bytes). Embodimentsare not limited to these examples.

It is noted that other configurations for the physical blocks 240-0,240-1, . . . , 240-M, rows 250-0, 250-1, . . . , 250-R, sectors 252-0,252-1, . . . , 252-S, and pages are possible. For example, the rows250-0, 250-1, . . . , 250-R of the physical blocks 240-0, 240-1, . . . ,240-M can each store data corresponding to a single logical sector whichcan include, for example, more or less than 512 bytes of data.

Consistent with descriptions thereof provided in the present disclosure,a solid state device can, in various embodiments, include a controlcomponent coupled to a number of solid state memory arrays in the solidstate device, where each array has multiple physical blocks of memorycells. Additionally, in various embodiments, each array can be formattedby the control component of the solid state device that is configured toaccess a defined set of data as a single object and store the definedset of data in the number of arrays as the single object.

As used herein, when it is stated that a solid state control componentcan perform an action, it will be understood as an abbreviatedsubstitute for “the control component that is configured to” or “thecontrol component that is configured to execute by way of a processor”.

In some embodiments, the control component of the solid state device caninclude an associated processor that manages the formatting of thesingle object. The formatting can be performed by determining in whichof the multiple physical blocks of memory cells in the number of solidstate memory arrays the defined set of data will be stored. For example,the control component of the solid state device can, in variousembodiments, store the defined set of data to a particular (e.g., whichcan be a predetermined or determined “on the fly”, as appropriate to thecircumstance) partition of the number of memory arrays of the physicalblocks of memory cells. The particular partition can be determined basedupon a number of factors, as described in the present disclosure. Suchfactors can, by way of example and not by way of limitation, include thewear (e.g., the number of write/erase cycles particular memoryarrays/blocks/cells have experienced), whether the cells of a particularblock/array are single-level or multi-level memory cells, and/or thetype of memory cell in the block/array, among other factors.

By way of example and not by way of limitation, the multiple physicalblocks of memory cells can be arranged in a non-volatile NAND or anon-volatile NOR architecture. In some embodiments, the controlcomponent of the solid state device can store the defined set of databeginning-to-end in a number of contiguous physical blocks of memorycells. For example, the contiguous physical blocks of memory cells canbe defined by the particular partition of the number of memory arrays ofthe physical blocks of memory cells. In some embodiments, the definedset of data can be a boot image, as described herein. In someembodiments, the defined set of data can be instructions for installingand/or initiating a number of operating systems, as described herein.The embodiments of defined sets of data are not so limited.

The control component of the solid state device can, in someembodiments, access the defined set of data and store the defined set ofdata in the number of arrays after completion of an atomic operation. Asappreciated by one of ordinary skill in the relevant art, a set ofoperations can be considered atomic when two conditions are met. First,until the entire set of operations is completed, no other process canknow about the changes being made undetectably. Second, if any of theoperations are unsuccessful, then the entire set of operations isaborted and the state of the system is restored to the state it was inbefore any of the operations began. In the present disclosure, accessingthe defined set of data in an atomic operation manner can, for example,prevent an access being terminated and/or interrupted prematurely, whichotherwise may result in a partial update and/or installation of thedefined set of data. If not for the atomic operation, a number ofnegative consequences could occur due to a partial write of criticaldata. Additionally, the control component of the solid state device can,in some embodiments, assign a pointer to a last known-good copy of thedata in the arrays until completion of the atomic operation, where thepointer directs a read of the data to be performed on the lastknown-good copy. A pointer to a last known-good object can be providedand maintained. That is, until a write process has been completedsuccessfully, any read attempt of the object can be directed by thepointer to the last known-good object.

Additionally, a solid state device can, in various embodiments, includea control component coupled to a number of solid state memory arrays inthe solid state device, where each array has multiple physical blocks ofmemory cells. Each array can, in various embodiments, be formatted bythe control component of the solid state device that is configured toaccess a defined set of data as a single object, where one or moreiterations of the defined set of data are accessed, and store multiplecopies of the one or more iterations to particular locations in thenumber of arrays as the single object. Accessing one or more iterationsof the defined set of data can, by way of example and not by way oflimitation, include downloading one or more copies of programinstructions from a network provider of such instructions and/or from ahost, as described in the present disclosure.

The control component of the solid state device can, in someembodiments, store each of the multiple copies in a physically differentarray of the number of arrays. By storing in the physically differentarray, faults confined to a certain array may be prevented fromcorrupting critical data stored in the physically different array.However, in some embodiments, possibly for reduction of space and/orcost, among other considerations, the number of arrays can be one. Aspreviously described, the control component of the solid state devicecan, in some embodiments, read the single object beginning-to-end in anumber of contiguous physical blocks of memory cells.

Multiple copies of the write object can be stored (e.g., simultaneouslyor sequentially). In the case of a flash memory device, the copies canbe stored in physically independent memory arrays to contribute tooverall reliability. In various embodiments, the object can be stored inmemory elements that have been determined to be most reliable withinand/or between various arrays of memory cells. For example, the data canbe stored in elements that are currently and/or are capable of storingone bit per memory cell rather than two or more.

The control component of the solid state device can, in someembodiments, store at least one of the multiple copies in physicalblocks of the array determined to be more reliable than other physicalblocks. For example, the physical blocks of the array determined to bemore reliable can be physical blocks having single-level memory cells.Such single-level memory cells can be capable of holding only one bit ofdata or they can be multi-level memory cells restrained from holdingmore than one bit of data. In any case, a cell having only one bit ofdata can be more reliable due to less likelihood of a notable shift incharge level affecting a read of the cell. In some embodiments, thephysical blocks of the array determined to be more reliable can bephysical blocks having memory cells that have been reused fewer timesthan memory cells of the other physical blocks (e.g., memoryblocks/cells that have experienced fewer write/erase cycles). The mannerof determining greater reliability of physical blocks of the array isnot limited by the examples just provided.

After the one or more iterations of the accessed data are accessed, insome embodiments, the control component of the solid state device canindependently verify multiple copies of the one or more data iterationsprior to storing the single object in the array. To independently verifycan be performed as operations described in the present application. Assuch, the control component of the solid state device can, in someembodiments, read and independently correct a number of errors foundprior to storing the single object in the array. After completion ofverifying the data iterations, the control component of the solid statedevice can assign a pointer to a particular copy of the one or more dataiterations as a new last known-good copy to replace a previous lastknown-good copy. The control component of the solid state device alsocan send a write completion acknowledgment to a host such that any readby the host is directed by the pointer to the new last known-good copy.

After an entire object has been received, each of the copies can beindependently verified. Verification can include at least reading anderror correcting the entire object. Moreover, thresholds can beimplemented by which fewer than a particular number of read errors aredetected before storing of an object in a solid state memory array isallowed.

In addition, an end-to-end data integrity check (e.g., a cyclicredundancy check (CRC)) can be calculated. In some embodiments, the CRCcan be embedded by the host before transmission to the solid statememory device. In brief, a CRC operation uses a mathematical calculationto verify data integrity after a transfer operation. A CRC is a type offunction that takes as input a data stream of any length, and producesas output a value of a certain space, commonly a 32-bit integer. Theterm CRC denotes either the function or the function's output. A CRC canbe used as a checksum to detect accidental alteration of data duringtransmission or storage. CRCs are popular because they are simple toimplement in binary hardware, are easy to analyze mathematically, andare particularly good at detecting common errors, for instance, causedby noise in transmission channels.

Consistent with descriptions thereof provided in the present disclosure,a system can, in various embodiments, include a host control componentthat is configured to be operably coupled to a host in order to manage asystem. Such a host, by way of example and not by way of limitation, caninclude maintaining intended operability of computing devices andsystems, portable or otherwise, as described herein. The host controlcomponent can be configured to be operably coupled to a controlcomponent of a solid state device having multiple solid state physicalmemory blocks of memory cells. Additionally, the control component ofthe solid state device can be configured to access a defined set of dataas a single object and manage the defined set of data as the singleobject during subsequent write and read operations.

The control component of the solid state device can, in someembodiments, store multiple copies of the single object where each ofthe multiple copies is separately stored in the multiple memory blocksas determined by a set of rules for writing to physically separatememory blocks. For example, the control component of the solid statedevice can, according to the set of rules, store the multiple copies ofthe single object in a particular partition of the multiple physicalmemory blocks of memory cells. As such, the control component of thesolid state device can, in some embodiments, store each of the multiplecopies of the single object in the particular partition contiguously ina number of the multiple physical memory blocks for end-to-end dataintegrity.

In addition or in the alternative, the control component of the solidstate device can, in some embodiments, write in the multiple physicalmemory blocks as determined by logical block addressing. As such, thecontrol component of the solid state device can, in some embodiments,store in particular logical block addresses.

As previously stated, block oriented memory devices may not be able toperform the range of operations and/or services described herein withregard to object oriented memory systems because block oriented memorydevices generally do not have a capability to be aware of the number oflogical blocks in a file and/or the order in which the blocks will beread and/or written. Block oriented memory devices generally onlyrespond to read/write commands. Nonetheless, as described in the presentdisclosure, when both the host and the solid state device follow a setof rules associated with block reads and writes to particular logicalblock addresses, a number of the operations and/or services describedherein with regard to object oriented solid state devices can beemulated. Such emulation can be accomplished when block oriented solidstate devices handle data in a prescribed manner.

For example, the block oriented device can define a series of blocknumbers to be reserved for the data. The data can be stored in theparticular series in a particular order, with the host providing anindicator to the solid state device of the last block of data. The solidstate device can manage multiple copies of the data as well as provideread access to the last known-good version of the data when required.Storing the data as such in a block oriented arrangement would allowreading of a defined set of data to be performed consecutively frombeginning-to-end as with an object oriented solid state device.

Hence, a system as described in the present disclosure can, in variousembodiments, include a host control component that is configured to beoperably coupled to a host in order to manage a system, as describedherein. The host control component can, in various embodiments, beconfigured to be operably coupled to a control component of a solidstate device having multiple solid state physical memory blocks ofmemory cells. The control component of the solid state device can beconfigured to access a defined set of data in a block oriented mannerand handle the defined set of data in the block oriented manner duringsubsequent write and read operations when a set of rules is followed bythe host control component and the solid state device control componentto store the defined set of data in particular logical block addresses.

The set of rules followed by the host control component and the solidstate device control component can, in various embodiments, allow awrite of the defined set of data in separate and non-partitionedphysical memory blocks in the multiple solid state device physicalmemory blocks (e.g., consistent with block oriented memory). However,the set of rules followed by the host control component and the solidstate device control component can, in various embodiments, include aparticular series of physical memory block numbers to store the definedset of data. Such rules can direct that the write of the defined set ofdata is performed in a particular order. Such rules also can direct thatthe host control component provides an indicator to the solid statedevice control component to identify a last block of the defined set ofdata. By following one or more of such rules, the solid state devicecontrol component can read the defined set of data consecutively from abeginning to an end of the defined set of data as if the defined set ofdata was stored in an object oriented manner.

In some embodiments, the solid state device control component can storemultiple copies of the defined set of data where each of the multiplecopies is separately stored to the multiple memory blocks as determinedby the set of rules. Additionally, the solid state device controlcomponent can, in some embodiments, manage the multiple copies of thedefined set of data to provide read access of the host control componentto a last known-good copy of the defined set of data.

FIG. 3 is a block diagram illustrating object oriented memory in solidstate devices in accordance with one or more method embodiments of thepresent disclosure. Unless explicitly stated, the embodiments describedherein are not constrained to a particular order or sequence.Additionally, some of the described embodiments, or elements thereof,can occur or be operated at the same, or at least substantially thesame, point in time.

The embodiment illustrated in FIG. 3 includes accessing a defined set ofdata as a single object in an atomic operation manner, where theaccessing is from a source other than a host, as shown in block 310. Invarious embodiments, the source can be, by way of illustration and notby way of limitation, a network 102 as described with regard to FIG. 1.In some embodiments, accessing the data from a source other than thehost can include accessing the data in a mobile system, where the mobilesystem can be selected from a group that includes: a digital camera; adigital music device; a network device; a mobile telephone; a personaldigital assistant device; and a laptop computer; among a number of otherpossible mobile systems.

An atomic operation is intended to be performed as described elsewhereherein. In some embodiments, accessing the defined set of data in theatomic operation manner can include using a pointer to a last known-goodversion of such data until initial access to the defined set of data iscomplete.

As shown in block 320, the embodiment includes storing the defined setof data in the system as the single object to a number of solid statememory blocks as formatted by a control component of a solid statedevice that includes the number of solid state memory blocks. In someembodiments, the storing can be performed once the atomic operation iscompleted. Storing the defined set of data to the number of memoryblocks can, in some embodiments, include storing multiple copies of thedefined set of data each to separate memory blocks after independentlyperforming an atomic operation on each of the multiple copies iscomplete.

The solid state device can, in some embodiments, provide a host with apreviously stored version of the defined set of data upon detectingmultiple read requests to a newly stored version of the defined set ofdata during a particular period of time. For example, in variousembodiments, the solid state device or the host can detect multiple readrequests to a newly stored boot image required for a booting operationin the system. Consequently, in some embodiments, the solid state devicecan provide the host with a last known-good version of a boot image.

In accordance with the teachings of the present disclosure, objectoriented memory can, in various embodiments, include accessing a definedset of data as a single object, where the accessing is from a sourceother than the host, and performing a read-verify operation on theaccessed defined set of data. Embodiments of particular read-verifyoperations are described in more detail below. The embodiment caninclude storing the defined set of data as the single object in a numberof memory blocks as formatted by a control component operably coupled toa solid state device that includes the number of solid state memoryblocks.

In some embodiments, the storing of the defined set of data as thesingle object is performed once the read-verify operation is completed.Performing the read-verify operation on the accessed data can, in someembodiments, include using a pointer to a last known-good version of apreviously stored defined set of the data until the read-verifyoperation on the accessed defined set of new data is completed and thestoring of the defined set of new data is completed.

When the solid state device has determined that an object was reliablywritten and verified, the solid state device can send a write completionacknowledgement to the host. Any reads after the acknowledgement is sentto the host would be made on the new object rather than on the previousknown-good object. Alternatively, the host can require controlling thetransition through a command, a register setting, or similarnotification to the solid state device before allowing the transition tooccur.

The read-verify operation can, in some embodiments, be independentlyperformed on multiple copies of the defined set of new data before awrite operation on each of the copies is performed, and subsequentlystoring copies of the defined set of new data in which the read-verifyoperation detected fewer than a particular number of errors. Someembodiments can include storing multiple copies of the defined set ofnew data once the read-verify operation is successfully completed. Someembodiments can include providing automatic fail-over to a read-verifiedcopy of the data when at least the particular number of errors isdetected in another of the multiple copies of the defined set of newdata. In particular, some embodiments can include providing automaticfail-over to a read-verified copy of the defined set of new data when aparticular number of new errors are detected in another previouslyread-verified and stored copy of the defined set of new data.Embodiments of performing the read-verify operation can includeperforming a cyclic redundancy checking (CRC) operation. Embodiments ofread-verify operations are not so limited.

Error detection operations can have the ability to detect the presenceof errors caused by noise or other impairments during transmission froma transmitter to a receiver. Error correction can have the additionalability to reconstruct the original, error-free data. Briefly, examplesof such, not by way of limitation, can include an automaticrepeat-request (ARQ) in which the transmitter sends the data and also anerror detection code, which the receiver can use to check for errors,and request retransmission of erroneous data. In some cases, the requestis implicit in that the receiver sends an acknowledgement (ACK) ofcorrectly received data, and the transmitter resends anything notacknowledged within a reasonable period of time.

Another example is forward error correction (FEC) in which thetransmitter encodes the data with an error-correcting code (ECC) andsends the coded message. The receiver might not send any messages backto the transmitter. The receiver can decode what it receives into the“most likely” data. The codes are designed so that it would take a largeamount of noise to trick the receiver into misinterpreting the data. Itis possible to combine the two, so that minor errors are correctedwithout retransmission, and major errors are detected and aretransmission is requested.

Some embodiments of the present disclosure can include performing anerror correction operation when a particular number of errors aredetected in at least one of a number of previously read-verified andstored copies of the defined set of data. Some embodiments perform theerror correction operation when a particular number of errors aredetected in at least one of a number of copies not-yet read-verified orstored copies of the defined set of data. Performing the errorcorrection operation can, in some embodiments, include performing abit-by-bit comparison of multiple previously read-verified and storedcopies of the defined set of data, where the solid state devicevalidates one or more copies from among the multiple copies by selectingfrom a majority of matching copies.

Other protections can include calculation of an arithmetic signature ofthe defined data set (e.g., a hash function, as appreciated by one ofordinary skill in the art). The solid state device can calculate, forexample, the hash function and then present the calculation back to thehost as part of the completion acknowledgement response. The host canthen make a decision whether the signature is correct. Reading theobject can also generate a data signature (e.g., a hash function) thatthe host can use as part of an authentication program. The signature caneither be calculated prior to sending the object data to the host or asthe object data is being sent and the signature would thus be availablefor the host to read from the solid state device.

Briefly, a hash function is a well-defined procedure or mathematicalfunction that converts a large, possibly variable-sized amount of datainto a small datum, usually a single integer that may serve as an indexinto an array. Hash functions are mostly used to speed up table lookupor data comparison tasks. Hash functions are related to checksums, checkdigits, fingerprints, randomizing functions, error correcting codes, andcryptographic hash functions. Although these concepts overlap to someextent, each has its own uses and requirements and all are within thescope of the present disclosure.

Having the device calculate the arithmetic signature (e.g.,automatically on power-up) can be used to authenticate the data beforeexecution of the encoded data. Such authentication can improve theoverall security of the system, for example, by preventing hackers frommodifying the code to gain access to a network and/or other operations.

Some embodiments of the present disclosure can include providing anarithmetic signature in the defined set of data prior to accessing thedata from the source, where the arithmetic signature is provided by thesolid state device back to the source for detection of errors. Tnaddition or in the alternative, some embodiments can include providingan arithmetic signature in the defined set of data prior to accessingthe data from the host, where the arithmetic signature is provided bythe solid state device back to the host for detection of errors.

The solid state device can calculate, for example, the hash function andthen present the calculation back to the host as part of the completionacknowledgement response. The host can then make a decision whether thesignature is correct. Reading the object can also generate a datasignature (e.g., a hash function) that the host can use as part of anauthentication program. The signature can either be calculated prior tosending the object data to the host, or as the object data is beingsent, and the signature would thus be available for the host to readfrom the solid state device.

Conclusion

The present disclosure includes methods, devices, and systems for objectoriented memory in solid state devices. One embodiment of a method forobject oriented memory in solid state devices includes accessing adefined set of data as a single object in an atomic operation manner,where the accessing is from a source other than a host. The embodimentalso includes storing the defined set of data as the single object in anumber of solid state memory blocks as formatted by a control componentof a solid state device that includes the number of solid state memoryblocks.

It will be understood that when an element is referred to as being “on,”“connected to” or “coupled with” another element, it can be directly on,connected, or coupled with the other element or intervening elements maybe present. In contrast, when an element is referred to as being“directly on,” “directly connected to” or “directly coupled with”another element, there are no intervening elements or layers present. Itwill be understood that when a first element is referred to as being“connected to” or “coupled with” another element, the first element isphysically attached to the other of the two elements is intended. Incontrast, when elements are referred to as being “operably coupled,” theelements are in communication with one another. As used herein, when itis stated that a solid state control component can perform an action, itwill be understood as an abbreviated substitute for “the controlcomponent that is configured to” or “the control component that isconfigured to execute by way of a processor”. As used herein, the term“or” by itself is inclusive of the plurality of linked elements, ratherthan being used in an exclusive manner, unless explicitly statedotherwise. Further, as used herein, the term “and/or” includes any andall combinations of one or more of the associated listed items.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements and that these elementsshould not be limited by these terms. These terms are only used todistinguish one element from another element. Thus, a first elementcould be termed a second element without departing from the teachings ofthe present disclosure.

In the detailed description of the present disclosure, reference is madeto the accompanying drawings that form a part hereof, and in which isshown by way of illustration how one or more embodiments of the presentdisclosure may be practiced. These embodiments are described insufficient detail to enable those of ordinary skill in the art topractice the embodiments of this disclosure, and it is to be understoodthat other embodiments may be utilized and that process, electrical, orstructural changes may be made without departing from the scope of thepresent disclosure.

As will be appreciated, elements shown in the various embodiments hereincan be added, exchanged, or eliminated so as to provide a number ofadditional embodiments of the present disclosure. In addition, as willbe appreciated, the proportion and the relative scale of the elementsprovided in the figures are intended to illustrate the embodiments ofthe present disclosure, and should not be taken in a limiting sense.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises” and“comprising,” as used in this specification, specify the presence ofstated features, integers, steps, operations, elements, or components,but do not preclude the presence or addition of one or more otherfeatures, integers, steps, operations, elements, components, or groupsthereof.

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by oneof ordinary skill in the art to which this disclosure belongs. It willbe further understood that terms, such as those defined in commonly useddictionaries, should be interpreted as having a meaning that isconsistent with their meaning in the context of the relevant art and thepresent disclosure, and should not be interpreted in an idealized oroverly formal sense unless expressly so defined herein.

Although specific embodiments have been illustrated and describedherein, those of ordinary skill in the relevant art will appreciate thatan arrangement calculated to achieve the same results can be substitutedfor the specific embodiments shown. This disclosure is intended to coverall adaptations or variations of various embodiments of the presentdisclosure.

It is to be further understood that the above description has been madein an illustrative fashion, and not a restrictive one. Combination ofthe above embodiments, and other embodiments not specifically describedherein, will be apparent to those of ordinary skill in the relevant artupon reviewing the above description.

The applicability of the various embodiments of the present disclosureincludes other applications in which the above methods, devices, andsystems are used, for example, in association with other computingsystems, mobile devices and/or systems, and the like. Therefore, theapplicability of various embodiments of the present disclosure should bedetermined with reference to the appended claims, along with the fullrange of equivalents to which such claims are entitled.

In the foregoing Detailed Description, various features are groupedtogether in a single embodiment for the purpose of streamlining thedisclosure. This method of disclosure is not to be interpreted asreflecting an intention that the disclosed embodiments of the presentdisclosure need to use more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject matterlies in less than all features of a single disclosed embodiment. Thus,the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment.

1. A method of object oriented memory in solid state devices,comprising: accessing a defined set of data as a single object in anatomic operation manner, wherein the accessing is from a source otherthan a host; and storing the defined set of data as the single object ina number of solid state memory blocks as formatted by a controlcomponent of a solid state device that includes the number of solidstate memory blocks.
 2. The method of claim 1, wherein the storing isperformed once the atomic operation is completed.
 3. The method of claim1, wherein accessing the defined set of data in the atomic operationmanner includes using a pointer to a last known-good version of suchdata until initial access to the defined set of data is complete.
 4. Themethod of claim 1, wherein storing the defined set of data to the numberof memory blocks includes writing multiple copies of the defined set ofdata each in separate memory blocks after independently performing anatomic operation on each of the multiple copies is complete.
 5. Themethod of claim 1, wherein the method includes the solid state deviceproviding the host with a previously stored version of the defined setof data upon detecting multiple read requests to a newly stored versionof the defined set of data during a particular period of time.
 6. Themethod of claim 5, wherein detecting multiple read requests to the newlystored version of the defined set of data includes the solid statedevice and/or the host detecting multiple read requests to a newlystored boot image required for a booting operation in a system managedby the host.
 7. The method of claim 6, wherein detecting multiple readrequests to the newly stored boot image includes the solid state deviceproviding the host with a last known-good version of a boot image. 8.The method of claim 1, wherein accessing data includes accessing thedata in a mobile system selected from a group including: a digitalcamera; a digital music device; a network device; a mobile telephone; apersonal digital assistant device; and a laptop computer.
 9. A method ofobject oriented memory in solid state devices, comprising: accessing adefined set of data as a single object, wherein the accessing is from asource other than a host; performing a read-verify operation on theaccessed defined set of data; and storing the defined set of data as thesingle object in a number of memory blocks as formatted by a controlcomponent operably coupled to a solid state device that includes thenumber of solid state memory blocks.
 10. The method of claim 9, whereinthe storing of the defined set of data as the single object is performedonce the read-verify operation is completed.
 11. The method of claim 9,wherein performing the read-verify operation on the accessed dataincludes using a pointer to a last known-good version of a previouslystored defined set of the data until the read-verify operation on theaccessed defined set of new data is completed and the storing of thedefined set of new data is completed.
 12. The method of claim 9, whereinthe method includes independently performing the read-verify operationon multiple copies of the defined set of new data before a writeoperation on each of the copies is performed and subsequently storingcopies of the defined set of new data in which the read-verify operationdetected fewer than a particular number of errors.
 13. The method ofclaim 12, wherein the method includes storing multiple copies of thedefined set of new data once the read-verify operation is successfullycompleted.
 14. The method of claim 13, wherein the method includesproviding automatic fail-over to a read-verified copy of the data whenat least the particular number of errors is detected in another of themultiple copies of the defined set of new data.
 15. The method of claim13, wherein the method includes providing automatic fail-over to aread-verified copy of the defined set of new data when at least aparticular number of new errors are detected in another previouslyread-verified and stored copy of the defined set of new data.
 16. Themethod of claim 9, wherein performing the read-verify operation includesperforming a cyclic redundancy checking operation.
 17. The method ofclaim 9, wherein the method includes performing an error correctionoperation when a particular number of errors are detected in at leastone of a number of previously read-verified and stored copies of thedefined set of data.
 18. The method of claim 17, wherein performing theerror correction operation includes performing a bit-by-bit comparisonof multiple previously read-verified and stored copies of the definedset of data, wherein the solid state device validates one or more copiesfrom among the multiple copies by selecting from a majority of matchingcopies.
 19. The method of claim 9, wherein the method includes providingan arithmetic signature in the defined set of data prior to accessingthe data from the source, wherein the arithmetic signature is providedby the solid state device back to the source for detection of errors.20. The method of claim 9, wherein the method includes providing anarithmetic signature in the defined set of data prior to accessing thedata from the host, wherein the arithmetic signature is provided by thesolid state device back to the host for detection of errors.
 21. A solidstate device, comprising: a control component coupled to a number ofsolid state memory arrays in the solid state device, wherein each arrayhas multiple physical blocks of memory cells and wherein the controlcomponent is configured to: access a defined set of data as a singleobject; and store the defined set of data in the number of arrays as thesingle object.
 22. The device of claim 21, wherein the control componentincludes an associated processor that manages formatting of the singleobject in the physical blocks of memory cells in the number of arrays.23. The device of claim 21, wherein the multiple physical blocks ofmemory cells are arranged in a non-volatile NAND or a non-volatile NORarchitecture.
 24. The device of claim 21, wherein the defined set ofdata is for a boot image or an operating system.
 25. The device of claim21, wherein the control component is configured to store the defined setof data in a particular partition of the number of memory arrays of thephysical blocks of memory cells.
 26. The device of claim 21, wherein thecontrol component is configured to store the defined set of databeginning-to-end in a number of contiguous physical blocks of memorycells.
 27. The device of claim 21, wherein the control component isconfigured to access the defined set of data and store the defined setof data in the number of arrays after completion of an atomic operation.28. The device of claim 27, wherein the control component is configuredto assign a pointer to a last known-good copy of the data in the arraysuntil completion of the atomic operation, wherein the pointer directs aread of the data to be performed on the last known-good copy.
 29. Asolid state device, comprising: a control component coupled to a numberof solid state memory arrays in the solid state device, wherein eacharray has multiple physical blocks of memory cells and wherein thecontrol component is configured to: access a defined set of data as asingle object, wherein one or more iterations of the defined set of dataare accessed; and store multiple copies of the one or more iterations toparticular locations in the number of arrays as the single object. 30.The device of claim 29, wherein the control component is configured tostore each of the multiple copies in a physically different array of thenumber of arrays.
 31. The device of claim 29, wherein the number ofarrays is one.
 32. The device of claim 29, wherein the control componentis configured to store at least one of the multiple copies in physicalblocks of the array determined to be more reliable than other physicalblocks.
 33. The device of claim 32, wherein the physical blocks of thearray determined to be more reliable are physical blocks havingsingle-level memory cells.
 34. The device of claim 32, wherein thephysical blocks of the array determined to be more reliable are physicalblocks having memory cells that have been reused fewer times than memorycells of the other physical blocks.
 35. The device of claim 29, whereinafter the one or more iterations of the accessed data are accessed, thecontrol component is configured to independently verify multiple copiesof the one or more data iterations prior to storing the single object inthe array.
 36. The device of claim 35, wherein the control component isconfigured to read and independently correct a number of errors foundprior to storing the single object in the array.
 37. The device of claim35, wherein the control component is configured to assign a pointer to aparticular copy of the one or more data iterations as a new lastknown-good copy to replace a previous last known-good copy.
 38. Thedevice of claim 37, wherein the control component is configured to senda store completion acknowledgment to a host such that any read by thehost is directed by the pointer to the new last known-good copy.
 39. Thedevice of claim 37, wherein the control component is configured to senda store completion acknowledgement response to a host that is delayeduntil a data protection operation is successfully completed.
 40. Thedevice of claim 29, wherein the control component is configured to readthe single object beginning-to-end in a number of contiguous physicalblocks of memory cells.
 41. The device of claim 29, wherein the controlcomponent is configured to automatically initiate a read operation basedupon a power-on reset and/or transition of a signal and the read data isautomatically sent to a host where it is used to boot the host or thedata is ignored if the data is not required by the host at that time.42. The device of claim 29, wherein the control component is configuredto save a new defined set of data as a last install and the last installconfiguration will be defined as a known-good copy after the new definedset of data has booted successfully as stored at least once.
 43. Asystem, comprising: a host control component that is configured to beoperably coupled to a host in order to manage a system; wherein the hostcontrol component is configured to be operably coupled to a controlcomponent of a solid state device having multiple solid state physicalmemory blocks of memory cells; and wherein the control component of thesolid state device is configured to access a defined set of data as asingle object and manage the defined set of data as the single objectduring subsequent write and read operations.
 44. The system of claim 43,wherein the control component of the solid state device is configured tostore multiple copies of the single object and wherein each of themultiple copies is separately stored in the multiple memory blocks asdetermined by a set of rules for writing to physically separate memoryblocks.
 45. The system of claim 44, wherein the control component of thesolid state device is configured to store the multiple copies of thesingle object in a particular partition of the multiple physical memoryblocks of memory cells.
 46. The system of claim 45, wherein the controlcomponent of the solid state device is configured to store each of themultiple copies of the single object in the particular partitioncontiguously in a number of the multiple physical memory blocks forend-to-end data integrity.
 47. The system of claim 45, wherein thecontrol component of the solid state device is configured to store inthe multiple physical memory blocks as determined by logical blockaddressing.
 48. The system of claim 47, wherein the control component ofthe solid state device is configured to store in particular logicalblock addresses.
 49. A system, comprising: a host control component thatis configured to be operably coupled to a host in order to manage asystem; wherein the host control component is configured to be operablycoupled to a control component of a solid state device having multiplesolid state physical memory blocks of memory cells; wherein the controlcomponent of the solid state device is configured to access a definedset of data in a block oriented manner and manage the defined set ofdata in the block oriented manner during subsequent write and readoperations; and wherein a set of rules is followed by the host controlcomponent and the solid state device control component to store thedefined set of data in particular logical block addresses.
 50. Thesystem of claim 49, wherein the set of rules followed by the hostcontrol component and the solid state device control component allows awrite of the defined set of data in separate and non-partitionedphysical memory blocks in the multiple solid state device physicalmemory blocks.
 51. The system of claim 49, wherein the set of rulesfollowed by the host control component and the solid state devicecontrol component includes a particular series of physical memory blocknumbers to write the defined set of data.
 52. The system of claim 51,wherein the write of the defined set of data is performed in aparticular order.
 53. The system of claim 52, wherein the write of thedefined set of data performed in the particular order includes the hostcontrol component providing an indicator to the solid state devicecontrol component to identify a last block of the defined set of data.54. The system of claim 53, wherein the solid state device controlcomponent is configured to read the defined set of data consecutivelyfrom a beginning to an end of the defined set of data as if the definedset of data was stored in an object oriented manner.
 55. The system ofclaim 49, wherein the solid state device control component is configuredto store multiple copies of the defined set of data and wherein each ofthe multiple copies is separately stored to the multiple memory blocksas determined by the set of rules.
 56. The system of claim 55, whereinthe solid state device control component is configured to manage themultiple copies of the defined set of data to provide read access of thehost control component to a last known-good copy of the defined set ofdata.